Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix bug in beta value computation #8466

Conversation

JosueNina
Copy link
Contributor

Description

This PR fixes a bug in the beta calculation logic. It ensures that the beta value is calculated correctly by processing data only when enough pairs of different symbols with the same date are available. Additionally, it now processes when at least "period + 1" correct pairs are available. The beta value is "fill-forwarded" until a valid pair is found, at which point it recalculates the beta.

Related Issue

Closes #8460

Motivation and Context

This change is required to ensure that the beta calculation logic works correctly and efficiently,

Requires Documentation Change

No documentation change required.

How Has This Been Tested?

It has been tested both in the cloud and locally. Additionally, a unit test has been added to ensure the correct functionality of the beta calculation. The test verifies that the logic correctly handles symbol pairs, computes the beta value, and processes the data only when enough valid pairs are available.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • Refactor (non-breaking change which improves implementation)
  • Performance (non-breaking change which improves performance. Please add associated performance test and results)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Non-functional change (xml comments/documentation/etc)

Checklist:

  • My code follows the code style of this project.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

- Beta is fill-forwarded
- A correct pair considered when they have different symbols and the
  same date
- Processing occurs when there are at least period+1 correct pairs
@JosueNina JosueNina force-pushed the bug-8460-beta-indicator-stuck-at-zero branch from 1d09f84 to bbb4ec0 Compare December 13, 2024 21:48
@JosueNina JosueNina force-pushed the bug-8460-beta-indicator-stuck-at-zero branch from 2485e58 to 834cff7 Compare December 16, 2024 15:27
- Remove effectiveResolution and Beta constructor parameter for
  resolution.
- Streamlined resolution handling logic for Beta indicator.
- Fixed issues with regression test for Beta.
@JosueNina JosueNina force-pushed the bug-8460-beta-indicator-stuck-at-zero branch from d17fd8d to 6c03643 Compare December 17, 2024 19:29
@JosueNina JosueNina force-pushed the bug-8460-beta-indicator-stuck-at-zero branch from a422ce7 to b35326c Compare December 18, 2024 17:32
@JosueNina JosueNina force-pushed the bug-8460-beta-indicator-stuck-at-zero branch from 5496967 to f1d8657 Compare December 19, 2024 18:50
@JosueNina JosueNina force-pushed the bug-8460-beta-indicator-stuck-at-zero branch from f1d8657 to 83117a5 Compare December 20, 2024 03:21
Copy link
Member

@Martin-Molinero Martin-Molinero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you 👍

@Martin-Molinero Martin-Molinero merged commit 3b559a5 into QuantConnect:master Dec 20, 2024
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Beta Indicator Can Get Stuck at Zero
2 participants